doc: fix incorrect formatting in browser docs. #24516
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![trop[bot]](https://avatars.githubusercontent.com/in/9879?s=60&v=4){kind=small}
Address incorrect typing for isEnabled. The root cause of this was due to missing backticks which caused the docs parser to think that the return type of the `isEnabled` function was null, where it was supposed to be a boolean type. The side effect of this was that the generated typescript typings were incorrect for this function. Fixes #24409
1 task
codebytere
approved these changes
Jul 10, 2020
|
Release Notes Persisted
|
codebytere
deleted the
trop/9-x-y-bp-doc-fix-incorrect-formatting-in-browser-docs--1594414672418
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #24473
See that PR for details.
Notes: Generated typing for win.isEnabled now is set to a boolean.